\section{Build a small pilot with CMDB}
\label{sec:cmdb_pilot}
In this part, we talk about the pilot we created with \textsf{ESP
Team}. This pilot concerns the \CMDB{} and how we can extract data
from that place to build the \SM{}.

\subsection{Extend Oracle schema}
\indent Historically the \CMDB{} took place when \MARS{} began to
follow ITIL recommandations\,\footnote{You can refer
section~\ref{sec:mars_itil} to learn more about ITIL and how \MARS{}
adapt it and work with it.}. It was probably answering all
requirements, but today, it can't be used for \SM{}, because it was
not designed for that job.

That's why discussion with \textsf{ESP Team} is engaged to use their
test instance database. As \tsf{ESP Team} is working to design the new
\CMDB{} version, we are in the loop to give them our inputs.

Firstly, we decided to captured all possible information from the key
users, or from global support teams. But, we can have a better impact
on stakeholders if the \SM{} is more simple, and only few
caracteristics need to be updated. This is one of the reason we decide
not to put all information in the \CMDB{} but only what is drawn on
\tsf{MS Visio} maps. Please, see
table~\ref{tab:properties_visio_database} on
page~\pageref{tab:properties_visio_database}.


\subsection{Populate the database}
\indent At the moment we are writing this document, the test instance
database of \CMDB{} is not available.

We choose to populate the databse, with only one business area to see
if the process can run in the near future.

\subsection{Extract from the database}
\indent \tsf{ESP Team} can set up automatic extracts from
\CMDB{}. They will build one extract on the table and fields that
\SM{} requiert. Then a future tool can import this extract and build
diagrams automatically\dots